System, Method and Computer Program Product for Receiving Data from a Satellite Radio Network

ABSTRACT

A system, method and computer program product are disclosed for receiving data from a satellite radio network in accordance with an embodiment of the present invention. In accordance with an embodiment of the present invention, a datagram broadcast via a satellite radio network is received utilizing a receiver. 
     The datagram includes broadcast identifier information that identifies a segment of receivers in the satellite radio network to which the datagram is directed. Utilizing the broadcast identifier information, a determination is made as to whether the recipient receiver is a member of the identified segment of receivers to which the datagram is directed. If the recipient receiver is determined to be a member of the identified segment of receivers to which the datagram is directed, then the datagram is processed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Pat. No. ______, currentlyU.S. application Ser. No. 12/053,533, entitled “System, Method AndComputer Program Product For Receiving Data From A Satellite Radio,”filed on Mar. 21, 2008, and allowed on Dec. 23, 2009, which applicationis a continuation of U.S. application Ser. No. 10/400,831, now U.S. Pat.No. 7,415,243, entitled “System, Method And Computer Program Product ForReceiving Data From A Satellite Radio,” filed on Mar. 27, 2003 andissued on Aug. 19, 2008, the contents of each of which are incorporatedin their entirety into this disclosure by reference.

BACKGROUND

This invention relates to broadcasting of data and more particularly tobroadcasting data to a defined group of remotely located recipients.

Satellite radio networks may be utilized to provide satellite digitalaudio services to compatible radio receivers. In a satellite radionetwork, the same data is typically simultaneously transmitted to allreceivers in the network so that all receivers receive the samebroadcast data. The general broadcast character of satellite radiotransmissions hinders the easy transmission of data that is intendedonly for a segment of the receivers especially when the amount of datato be transmitted is large.

Many of today's satellite radio receivers are being installed inautomobiles and other vehicles. Because of the increasing number ofvehicles with satellite radio receivers, automobile manufactures arebeing presented with a potentially useful way of providing informationto users of their vehicles. For example, to the automobilemanufacturers, it may be extremely desirable to deliver service and/orrecall information to their vehicles' users via satellite radio.

Most service and recall information, however, is directed at aparticular make and model of vehicle and rarely applies to all vehicleshaving a satellite radio receiver (let alone all vehicles of aparticular manufacturer). Unfortunately, the difficulty in deliveringinformation to a targeted segment of satellite radio receivers providesa difficult challenge in providing such service and/or recallinformation to a targeted segment of recipient vehicles.

In addition, today's satellite radio networks fail to provide a meansfor permitting changing or updating of the group of intended recipients.For example, once a vehicle has been repaired after receiving a serviceor recall notification via satellite radio, the vehicle may no longer bean intended recipient to a subsequent reminder message directed to thosevehicles that have not yet been serviced. Receiving such a remindermessage could lead to annoying or confusing users of an already servicedvehicle.

SUMMARY

A system, method and computer program product are disclosed forreceiving data from a satellite radio network in accordance with anembodiment of the present invention. In accordance with an embodiment ofthe present invention, a datagram broadcast via a satellite radionetwork is received utilizing a receiver. The datagram includesbroadcast identifier information that identifies a segment of receiversin the satellite radio network to which the datagram is directed.Utilizing the broadcast identifier information, a determination is madeas to whether the recipient receiver is a member of the identifiedsegment of receivers to which the datagram is directed. If the recipientreceiver is determined to be a member of the identified segment ofreceivers to which the datagram is directed, then the datagram isprocessed.

In one embodiment, the recipient receiver may be located in a vehicle.In another embodiment, the broadcast identifier information of thedatagram may be compared with locally stored identifier information ofthe recipient receiver to determine if the recipient receiver is amember of the identified segment of receivers to which the datagram isdirected. In an additional embodiment, the broadcast identifierinformation may include information identifying a geographic area towhich the datagram is directed. In such an embodiment, the broadcastidentifier information may be compared with information about ageographic location of the recipient receiver to determine whether therecipient receiver is in the geographic area to which the datagram isdirected. As a further option in such an embodiment, the geographiclocation information of the recipient receiver may be obtained utilizinga global positioning system.

In a further embodiment, the broadcast identifier information mayinclude information that identifies a subject matter of the datagram. Insuch an embodiment, the broadcast identifier information may be comparedwith locally stored identifier information of the recipient receiver todetermine whether the datagram is directed to the recipient receiver. Insuch an embodiment, a user of the recipient receiver may be able todefine at least a portion of the locally stored identifier informationthat is compared with the broadcast identifier information.

In an embodiment, the datagram may include an instruction to modify atleast a portion of locally stored identifier information of therecipient receiver. In such an embodiment, the processing of thedatagram may include modifying the locally stored identifier informationaccording to the instruction. As an option, a modified portion of thelocally stored identifier information may define at least one segment ofreceivers in the satellite radio network to which the recipient receiverbelongs. As another option, a contact may be notified upon modificationof the locally stored identifier information. In such an embodiment, thecontact may be notified via a cellular wireless communication link.

In another embodiment, the processing of the datagram may includestoring the datagram in memory. In an additional embodiment, theprocessing of the datagram may include informing a user of the recipientreceiver of the receipt of the datagram. In yet a further embodiment,the processing of the datagram may include determining whether apreviously received copy of the datagram is stored in memory coupled tothe recipient receiver. In such an embodiment, a determination may bemade as to whether the received datagram includes information forupdating and/or deleting the previously received copy of the datagramstored in memory. In even another embodiment, an instruction to modifyat least a portion of locally stored identifier information of therecipient receiver may be received via a cellular wireless communicationlink. In this embodiment, the locally stored identifier information maythen be modified according to the instruction.

In one embodiment, a modified portion of the locally stored identifierinformation may define at least one segment of receivers in thesatellite radio network to which the recipient receiver is a member. Inan additional embodiment, the datagram may include audio information andthe processing of the datagram may include presenting the audioinformation of the datagram utilizing an audio component coupled to therecipient receiver. In a further embodiment, the datagram may includevisual information that may be presented utilizing a visual componentcoupled to the recipient receiver during the processing of the datagram.

In one embodiment, diagnostic information may also be collected about avehicle in which the recipient receiver is located. In such anembodiment, the processing of the datagram may include a determinationas to whether information in the datagram relates to the collecteddiagnostic information, and if so, presenting the information of thedatagram relating to the diagnostic information to a user of therecipient receiver.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of a process for receiving data from a satelliteradio network in accordance with an embodiment of the present invention;

FIG. 2 is a flowchart of a process for receiving data from a satelliteradio network in accordance with an embodiment of the present invention;

FIG. 3 is a schematic diagram of a system for delivering and receivingdata broadcast via a satellite radio network in accordance with anembodiment of the present invention;

FIG. 4 is a schematic diagram of an exemplary receiver in accordancewith an illustrative embodiment of the present invention;

FIG. 5 is a flowchart of a process for receiving data broadcast via asatellite radio network in accordance with an exemplary embodiment ofthe present invention;

FIG. 6 is a depiction of three exemplary scenarios for identifierconfirmation in determining whether a received data packet is directedat the recipient receiver in accordance with an embodiment of thepresent invention; and

FIG. 7 is a flowchart of a process for enabling communication between areceiver receiving a datagram broadcast via a satellite radio networkand a remote location in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

FIG. 1 is a flowchart of a process 100 for receiving data from asatellite radio network in accordance with an embodiment of the presentinvention. In operation 102, a datagram broadcast via a satellite radionetwork is received utilizing a receiver. The datagram includesbroadcast identifier information that identifies a segment of receiversin the satellite radio network to which the datagram is directed. In oneembodiment, the recipient receiver may be located in a vehicle. As anoption, the datagram may be checked for transmission errors uponreceipt. In one such embodiment, the datagram may include a check sumthat is utilized in checking the received datagram has transmissionerrors.

As set forth in operation 104 of FIG. 1, a determination is madeutilizing the broadcast identifier information to determine whether therecipient receiver is a member of the identified segment of receivers towhich the datagram is directed. In one embodiment, the broadcastidentifier information of the datagram may be compared with locallystored identifier information of the recipient receiver to determine ifthe recipient receiver is a member of the identified segment ofreceivers to which the datagram is directed.

In an additional embodiment, the broadcast identifier information mayinclude information identifying a geographic area to which the datagramis directed. In such an embodiment, the broadcast identifier informationmay be compared with information about a geographic location of therecipient receiver to determine whether the recipient receiver is in thegeographic area to which the datagram is directed. As a further optionin such an embodiment, the geographic location information of therecipient receiver may be obtained utilizing a global positioningsystem. For example, in such an embodiment, the recipient receiver maybe coupled to a GPS receiver capable of receiving GPS information from aGPS transmitter (such as, e.g., a GPS satellite) or, as another option,directly from a satellite in the satellite radio network.

In a further embodiment, the broadcast identifier information mayinclude information that identifies a subject matter of the datagram. Insuch an embodiment, the broadcast identifier information may be comparedwith locally stored identifier information of the recipient receiver todetermine whether the datagram is directed to the recipient receiver.Additionally, a user of the recipient receiver may also be able todefine at least a portion of the locally stored identifier informationthat is compared with the broadcast identifier information.

With continuing reference to FIG. 1, if the recipient receiver isdetermined to be a member of the identified segment of receivers towhich the datagram is directed, then the datagram is processed inoperation 106. In one embodiment, the processing of the datagram mayinclude storing the datagram in memory. In another embodiment, theprocessing of the datagram may include informing a user of the recipientreceiver of the receipt of the datagram.

In a further embodiment, the datagram may include an instruction tomodify at least a portion of locally stored identifier information ofthe recipient receiver. In such an embodiment, the processing of thedatagram may include modifying the locally stored identifier informationaccording to the instruction. As an option, a modified portion of thelocally stored identifier information may define at least one segment ofreceivers in the satellite radio network to which the recipient receiverbelongs. As another option, a contact (such as, for example, a servicecenter, a dealer, a manufacturer, a satellite radio network provider, alocation or node in the satellite radio network such as a radio station,and/or even a user of the recipient receiver) may be notified uponmodification of the locally stored identifier information. In such anembodiment, the contact may be notified via a cellular wirelesscommunication link. In one embodiment, the datagram may be broadcast viaa non-satellite radio transmission or other type of general broadcasttransmission.

In one embodiment, the processing of the datagram may includedetermining whether a previously received copy of the datagram is storedin memory coupled to the recipient receiver. In such an embodiment, adetermination may be made as to whether the received datagram includesinformation for updating and/or deleting the previously received copy ofthe datagram stored in memory. In even another embodiment, aninstruction to modify at least a portion of locally stored identifierinformation of the recipient receiver may be received via a cellularwireless communication link. In this embodiment, the locally storedidentifier information may then be modified according to theinstruction.

In another embodiment, diagnostic information may also be collectedabout a vehicle in which the recipient receiver is located. In such anembodiment, the processing of the datagram may include a determinationas to whether information in the datagram relates to the collecteddiagnostic information, and if so, presenting the information of thedatagram relating to the diagnostic information to a user of therecipient receiver.

In a further embodiment, a modified portion of the locally storedidentifier information may define at least one segment of receivers inthe satellite radio network to which the recipient receiver is a member.In an additional embodiment, the datagram may include audio informationand the processing of the datagram may include presenting the audioinformation of the datagram utilizing an audio component coupled to therecipient receiver. In a further embodiment, the datagram may includevisual information that may be presented utilizing a visual componentcoupled to the recipient receiver during the processing of the datagram.

In an embodiment of the present invention, the processing of thereceived datagram may include making a determination as to whether acopy of datagram has been previously stored in a memory of the recipientreceiver. In an aspect of such embodiment, the broadcast identifierinformation of the received datagram may includes a data identifier(such as, e.g., a serial number) associated with content of thedatagram. In this aspect, the data identifier of the received datagrammay be compared with the data identifiers of datagrams already stored inthe memory of the recipient receiver to determine whether a copy of thedatagram has been previously stored in the memory. As a further option,data identifier of the received datagram may include information forindicating to the recipient receiver whether the previously stored copyof the datagram needs to be updated (i.e., replaced with the receiveddatagram) or deleted from memory.

FIG. 2 is a flowchart of a process 200 for receiving data from asatellite radio network in accordance with an embodiment of the presentinvention. In operation 202, a datagram broadcast via a satellite radionetwork may be received utilizing a receiver in a vehicle. The datagrammay have a header portion that includes a first group identifieridentifying a group of one or more receivers in the satellite radionetwork to which the datagram is directed, and an area identifieridentifying a geographic area in which the datagram is directed. Inoperation 204, information about a geographic location of the recipientreceiver may be obtained utilizing a global positioning system receivercoupled to the recipient receiver.

In this embodiment, the receiver may have a locally stored individualidentifier and a locally stored group identifier associated therewithand which are stored in a memory coupled to the receiver. To determineif the recipient receiver is an intended recipient of the datagram, thegroup identifier and the area identifier of the datagram may be comparedto the locally stored group identifier and obtained geographic locationinformation of the recipient receiver in operation 206.

The datagram may also have a body portion that includes a set of one ormore individual identifiers of receivers in the satellite radio networkand an instruction for replacing the locally stored group identifiers ofthe receivers identified by the set of one or more individualidentifiers with a second group identifier. In operation 208, acomparison of the locally stored individual identifier of the recipientreceiver to the set of one or more individual identifiers of thedatagram may then be performed to determine whether the locally storedindividual identifier of the recipient receiver matches at least oneindividual identifier in the set of one or more individual identifiersof the datagram. If a match is found, then the locally stored groupidentifier of the recipient receiver may be replaced with the secondgroup identifier of the datagram in operation 210.

FIG. 3 is a schematic diagram of system 300 for carrying out embodimentsof the present invention. System 300 comprises a satellite radio networkthat provides for satellite radio transmissions of data from one node(e.g., server 302) to one more other nodes (e.g., vehicles 304 and 306).The satellite radio network may include orbiting satellites 308 andEarth located satellite transmitters 310. The satellite radio networkmay also include terrestrial repeaters (including non-line of sightrepeaters) capable of receiving and retransmitting the datagram in orderto facilitate reliable reception in geographic areas where line of sightreception from the satellites 308 may be obstructed. As an option, acellular wireless link 312 may also be available between a vehicle 304and another node 302.

The data being transmitted may comprise one or more datagrams (i.e.,packets of data). FIG. 3 also illustrates an exemplary embodiment of adatagram 314. Datagram 314 may comprise a header and a body portion (ordata portion) 316. The header of the datagram may include a broadcastidentifier (broadcast ID) 318. The broadcast identifier 318 may compriseone or more of the following identifiers including, for example: anindividual identifier (individual ID) 320, a group identifier (group ID)322, a category identifier (category ID) 324, an area identifier (areaID) 326, a data identifier (data ID) 328, and a vehicle identifier(vehicle ID) 329.

The individual identifier 320 may identify an individual node orreceiver in the satellite radio network to which the datagram 314 isdirected. In an exemplary embodiment, the individual identifier 320 maycomprise or relate to a serial number of particular receiver. Thus, ifthe datagram 314 is targeted for a single specific recipient, a sender(e.g., server 302) may include the individual identifier 320 in thebroadcast identifier 318 of the datagram 314.

The group identifier 322 may define a group of nodes for which thedatagram 314 is directed. In an illustrative embodiment, some examplesof possible groups which may be defined by the group identifier 322include: a model year of a vehicle (e.g., 2003, 2002, 2001, etc.), aparticular model or vehicle type (e.g., Acura RL, Acura TL, HondaAccord, Honda CR-V, etc.), a feature or variation included in a vehicle(e.g., vehicles that include an onboard navigation system such as a NAVIbrand system or OnStar brand system), a service area (e.g., TorranceAcura, Detroit Honda, etc.), the maintenance history of a vehicle (e.g.,whether or not a vehicle has been repaired in response to a vehiclerecall), and a geographic location in which an owner (or other user) ofthe vehicle resides (e.g., Los Angeles, Torrance, San Francisco, etc.).With a group identifier 322 included in the broadcast identifier 318 ofsingle datagram 314, a sender may direct the datagram 314 to a specificset of receivers that are members of the group associated with the groupidentifier 322.

In one embodiment, the broadcast identifier 318 may include a pluralityof group identifiers 322 to define a subgroup of a particular group. Forexample, a group identifier associated with vehicles of model year 2002and a group identifier associated with Honda Accord model vehicles maybe both included in the broadcast identifier 318 of a datagram 314 todirect the datagram 314 to 2002 Honda Accord vehicles. In a specificaspect of this embodiment, the group identifiers 322 may be combined inthe broadcast identifier 318 with the user of an “AND” function in thebroadcast identifier (e.g., group identifier for 2002 model yearvehicles AND group identifier for Honda Accords).

The category identifier 324 may identify a particular category of whichthe datagram 314 is associated. The category identifier 324 may providegeneral information about the contents of the data 316 included in thedatagram 314. For example, the category identifier 324 may be indicatethat the contents of the datagram 314 relate to a service reminder forthe vehicle, news information, an advertisement and so on.

The inclusion of a category identifier 324 in the broadcast identifier318 may be used to help a user to selectively filter datagrams targetedto the user which are received by the user's receiver. For example, theuser may select to not receive datagrams that include advertisements(which are identified as advertisements by their category identifier).As a result, the user's receiver may be able to filter out the datagramscontaining advertisements by simply comparing the category identifier324 of the received datagram with a stored list of category identifiersthat the user does not want to receive.

The area identifier 326 may define a particular geographic location,region or area (e.g., Minneapolis, California, Eastern USA, etc) towhich the datagram 314 is directed. Thus, if the datagram 314 istargeted for all nodes located in a specific geographic location, regionor area, a sender may include the area identifier 326 in the broadcastidentifier 318 of the datagram 314.

The data identifier 328 may identify the contents of the datagram 314(i.e., the data 316 in the body of the datagram). In one embodiment, thedata identifier 328 may be a serial number associated with the contentsof the datagram 314. The data identifier 328 may also include versioninformation about the contents of the datagram 314 which may be used todetermine whether the contents of the datagram 314 are an updatedversion of a previously received datagram.

The vehicle identifier 329 may indicate a current condition of vehiclesto which the datagram is directed. For example, the vehicle identifier329 may be utilized to direct a datagram 314 to vehicles having anodometer reading between 7400 miles and 7600 miles. The receiver 330then be able to filter the datagram by comparing the vehicle identifierto information about the condition or status of its associated vehicle304 (e.g., the odometer reading of the vehicle 304) to determine if thereceiver 330 is an intended recipient of the datagram 314.

FIG. 3 further illustrates a satellite radio network receiver 330 forreceiving datagrams 314 broadcast via the satellite radio network.Receiver 330 may be included in at least a portion of the nodes in thesatellite radio network (e.g., vehicles 304 and 306). Receiver 330 mayhave an antenna 332 coupled thereto for aiding reception of a datagram314 broadcast via the satellite radio network. A user interface 334 mayalso be coupled to the receiver 330 to facilitate user control andinteraction therewith and for presenting information associated withreceived datagram 314 to the user. The receiver 330 may also be incommunication with other devices/components 336 (e.g., an embeddedcellular unit, personal digital assistant (PDA), a user's cellularphone/device, a computer, etc.) for permitting transmission of datatherebetween.

Receiver 330 also has locally stored identifier information 338 whichmay be stored in a memory of the receiver 330. In one embodiment, thelocally stored identifier information 338 may comprise a locally storedindividual identifier 340 associated with the receiver 338, one or morelocally stored group identifiers 342 associated with the receiver and,as a further option, one or more locally stored category identifiers 344associated with the receiver 330. In an exemplary embodiment, thelocally stored individual identifier 340 may be a unique serial numberassociated with the receiver 330. The one or more locally stored groupidentifiers 342 of the receiver 330 identify the groups of which thereceiver 330 is a member or with which the received is associated. Theone or more locally stored category identifiers 344 identify thecategories or subjects of data that the user is interested in receivingand/or wishes not to receive. As an option, the locally categoryidentifiers 344 may be selected by a user from a set of categoryidentifiers provided by the receiver 330 and/or the locally categoryidentifiers 344 may be defined by the user. The user may carry out thisselection and/or defining of the locally stored category identifiers 344via the user interface 334.

As a further option, the locally stored identifier information 338 mayfurther comprise a locally stored vehicle identifier 346 that isassociated with a current condition of the vehicle 304. The locallystored vehicle identifier 346 may be generated based on informationpertaining to the status or current condition of the vehicle 304collected by sensors and detectors in the vehicle 304 in communicationwith the receiver 330. For example, mileage information collected fromthe vehicle's odometer may be used to generate a corresponding locallystored vehicle identifier 346. The receiver 330 may then compare thelocally stored vehicle identifier 346 with the vehicle identifier 329 ina received datagram 314 to determine if the datagram is directed at thereceiver 330 of the vehicle 304.

include which may be stored in a memory of the receiver 330. In oneembodiment, the locally stored identifier information 338 may comprise alocally stored individual identifier 340 associated with the receiver338, one or more locally stored group identifiers 342 associated withthe receiver and, as a further option, one or more locally storedcategory identifiers 344 associated with the receiver 330. The vehicleidentifier 329 may define a particular group of vehicles based on acurrent condition of the vehicle. For example, the vehicle identifier329 may be utilized to direct a datagram 314 to vehicles having anodometer reading between 7400 miles and 7600 miles. The receiver 330then be able to filter the datagram by comparing the vehicle identifierto information about the condition or status of its associated vehicle304 (e.g., the odometer reading of the vehicle 304) to determine if thereceiver 330/vehicle 304 is an intended recipient of the datagram 314.

Receiver 330 may also be adapted for obtaining information correspondingto a current (or at least near-current) geographic location of thereceiver 330. In one embodiment, geographic location information may beobtained utilizing a global positioning system (GPS). For example, therecipient receiver 330 may have a GPS receiver coupled thereto that iscapable of receiving GPS information from a GPS transmitter (such as,e.g., a GPS satellite) or, as another option, directly from a satellitein the satellite radio network (e.g., satellite 308). As an option, thereceiver 330 may correlate the obtained geographic location to an areaidentifier pre-associated with the geographic location from a localdatabase of area identifiers and their corresponding pre-associatedgeographic locations. In such an embodiment, the correlated areaidentifier may be compared with an area identifier 326 of a receiveddatagram 314 to determine if the area identifiers match and, if theymatch, indicate that receiver 330 is in a geographic location for whichthe datagram 314 is directed.

With continuing reference to FIG. 3, server 302 may include logic forgenerating the broadcast identifier 318 included in a datagram 314 andthereby permit a user (via a user interface coupled to the generatinglogic of the server 302) to define the segment of receivers in asatellite radio network to which the datagram 314 is directed identifiedby the broadcast identifier 318. Once the broadcast identifier of adatagram has been defined, the datagram can be broadcast over thesatellite radio network via a transmitter (e.g., transmitter 310)coupled to the server 302. Server 302 may also include logic adapted forreceiving notifications sent by the targeted receivers (i.e., receiversin the segment of receivers for which the datagram is directed). In anexemplary embodiment, the notifications may be transmitted via thecellular wireless communication link 312. In one embodiment, thenotifications may indicate that the responding receivers have receivedthe datagram (i.e., a confirmation of receipt). In embodiments where thedatagram 314 includes an instruction to modify locally stored identifierinformation in the targeted receivers, the notification may be sent tothe server 302 after modification of the locally stored identifierinformation in the responding receiver. Server 302 may also maintain adatabase of information relating to at least a portion of the receiversin the satellite radio network. This database may be updated uponreceipt of the notifications sent by the receivers.

Through the use of embodiments of the system 300 set forth in FIG. 3, adatagram 314 directed to a selected segment of receivers may be sent ina single broadcast over the satellite radio network. However, since itis possible to imagine situations where an intended receiver is turnedoff or otherwise not able to receive datagrams broadcasted via thesatellite radio network, it may be necessary to transmit the datagrammore than once (i.e., multiple times) over a period of time and/or atdifferent times in a day.

FIG. 4 is a schematic diagram of an exemplary receiver 330 in accordancewith an illustrative embodiment of the present invention. In thisillustrative embodiment, satellite radio antenna 332 may be coupled to asatellite radio receiver component 402 adapted for receiving datagramsbroadcast via a satellite radio network. Satellite radio receivercomponent 402 may be coupled to the user interface 334 which may be, forexample, an vehicular audio head unit for providing data (such as, e.g.,audio information) to the user interface 334.

Exemplary receiver 330 may also include a processor (e.g., centralprocessing unit (CPU)) 404. Satellite radio receiver component 402 maybe coupled to the processor 404 for providing data received by thesatellite radio receiver component 402 to the processor 404. As anoption, receiver 330 may also have a buffer memory 406 interposedbetween the processor 404 and satellite radio receiver component 402 fortemporally storing data being transmitted from the satellite radioreceiver component 402 to the processor 404. Receiver 330 may also havelocal memory 408 coupled to the processor 404 for storing data therein.In an exemplary embodiment, local memory 408 may be of a type of memorycapable of storing data even when power to the receiver 330 is turnedoff. In one embodiment, the local memory 408 may comprise a flash typeof memory. Local memory 408 may store therein local identifierinformation of the receiver 330, text message data and voice messagedata with message identifier information, software for operating andcontrolling the receiver 330. In one embodiment, when local memorybecomes full, data stored therein may be automatically deleted startingwith oldest data (the data that has been stored the longest) first. Inaddition, receiver 330 may permit data stored in local memory to beread, rewritten, deleted from data received from the other components336 coupled to the receiver 330.

With continuing reference to FIG. 4, receiver 330 may also have a sensorinterface 410 for coupling the receiver 330 to diagnostic and othersensors 412 in the hosting vehicle (e.g., vehicle 304) to permittransmission of diagnostic, status and other data about the vehiclecollected by the sensors 412 to the receiver 330. In an illustrativeembodiment, the sensor interface 410 may comprise a Control Area Networkbus (CANbus).

Receiver 330 may have a power supply 414 that is coupled to an externalpower supply 416. In an exemplary embodiment where the receiver 330resides in a vehicle, the external power supply 416 may include anignition power supply (IG) and/or an accessory power supply (ACC). In anillustrative exemplary embodiment of the receiver 330 illustrated inFIG. 4, receiver 330 may be activated by turning on power supply (IGand/or ACC) 416 upon which time the receiver 402 may be set to receivedata from satellite radio network broadcasts. The receiver 330 may savereceived data while simultaneously receiving satellite radio music anddata. As an option, the receiver 330 may be able to temporarily cancelsatellite radio network data reception and saving process whendownloading software onto the memory of the receiver 330 and/or when thereceiver 330 is performing large amounts of processing (i.e., heavyprocessing).

As illustrated in FIG. 4, receiver 330 may also include a plurality ofinterfaces 418, 420, 422, 424, 426, 428 for coupling the receiver 330 tothe user interface 334 and other components 336 in the hosting vehicle(e.g., vehicle 304). In an exemplary embodiment, interfaces may includeserial interfaces (e.g., RS232C interfaces 420, 424, 426) and otherinterfaces (e.g., audio interfaces 418 and 428 and Bluetooth interface422). In the illustrated exemplary embodiment, audio interface 428 maycomprise an audio bus for aiding control of audio portions of userinterface 334. Additionally in this exemplary embodiment, components 336may include a cellular communication component 430 for cellular wirelesscommunication, a computer component 432 (e.g., a PDA and/or PC), asubscriber mobile assistance component (SMAC) 434 (e.g., an OnStarsystem component), and a navigation/location component 436 (which mayalso include a personal computer element) for providing navigational andlocation information to a user (e.g., GPS component, NAVI brandnavigation system, etc.).

In an exemplary embodiment, the user interface 334 may be utilized todisplay textual information and voice message replay functions. Via theuser interface 334, a user may be able to control information handled bythe receiver 330 such as controlling the selecting and displaying oftext messages and open display of messages, selecting and replaying orcanceling of voice messages, and controlling voice output via “text tospeech” and voice output via “MP3” data replay.

In such an illustrative embodiment, receiver 330 may received inputsfrom via cellular component 430 via interface 422. These inputs mayinclude point of interest (POI) information, software downloads, andmessage data. Via the interface 422, the receiver 330 may output to thecellular component 430 information such as telephone numbers, identifierinformation to confirm reception of satellite radio network data,vehicle diagnosis/sensor data and other forms of message data suitablefor transmission via a cellular wireless communication link. Cellularcomponent 430 may also be utilized to receive software updates andadditional support relating to release data compression, data coding,voice data replay formats, cellular/PDA/PC communication formats,vehicle diagnosis/sensor data input formats and timing changes, andnavigation component 436 updates.

Via interface 424, receiver 330 may receive POI information from thesubscriber mobile assistance component 434 and output informationsimilar to that output to the cellular component 430 but suitable fortransmission via the subscriber mobile assistance component 434.Receiver 330 may receive via interface 426 POI information and softwaredownloaded by navigation/location component 436 while providing thenavigation/location component 436 information obtained from thesatellite radio network data and the cellular component 430.

FIG. 5 is a flowchart of a process for receiving and storing databroadcast via a satellite radio network in accordance with an exemplaryembodiment of the present invention. When a packet of data (i.e., adatagram) is broadcast via a satellite radio network, the received datamay first be checked for errors (see operations 502, 504, 506). Aftererror checking, the broadcast identifier information of the receiveddata packet is confirmed and compared with locally stored identifierinformation of the receiver to determine if the data packet is directedat the receiving vehicle and receiver (see operations 508, 510, 512). Ifthe received data packet is intended for another component in thevehicle (that is in communication with the receiver), the data packetmay be forwarded to the intended component in operation 514. Inoperation 516, the received data packet is analyzed to determine if itcontains instructions for changing a locally stored group identifierassociated with the receiver, and if so, the locally stored groupidentifier of the receiver is changed according to the instructions ofthe received data packet in operation 518.

The broadcast identifier information of received data packet may also beanalyzed to determine if a data identifier of the received data packetmatches a data identifier of a data packet already stored in the memoryof the receiver in operation 520. If no match to the data identifier ofthe received data packet can be found in the memory of the receiver,then the received data packet is stored in the memory in operation 522.On the other hand, if the data identifier of the received data packet isdetermined to match a data identifier of a data packet already stored inthe memory of the receiver, then a determination is made as to whetherthe locally stored version of the data packet is to be deleted orupdated by the received data packet (see operations 524, 526, 528). Inthe exemplary embodiment, received data packet may be analyzed todetermine if it contains a delete or update flag in order to determinewhether the locally stored version of the data packet is to be deletedor updated by the received data packet.

FIG. 6 is a depiction of three exemplary scenarios 602, 604, 606 foridentifier confirmation (operation 508) in determining whether areceived data packet is directed at the recipient receiver in accordancewith an embodiment of the present invention.

In the first scenario 602, the broadcast identifier information of thereceived data packet may include both a group identifier and an areaidentifier. If both the group identifier and the area identifier of thereceived data packet match a group identifier and area identifierlocally stored in the recipient receiver, then the data packet isdetermined to be directed at the recipient receiver and vehicle. Ifeither or both identifiers of the data packet do not match the locallystored group identifier and area identifier, then the data packet isdetermined to not be directed at the recipient receiver and vehicle. Aspreviously set forth, the locally stored area identifier may be derivedfrom location data obtained from a GPS or the broadcasting satellite.

In the second scenario 604, the broadcast identifier information of thereceived data packet may include either a group identifier or an areaidentifier (but not both). If either the group identifier and the areaidentifier of the received data packet match the locally stored groupidentifier and the area identifier respectively, then the data packet isdetermined to be directed at the recipient receiver and vehicle. Ifneither identifiers of the data packet match the locally stored groupidentifier and area identifier, then the data packet is determined tonot be directed at the recipient receiver and vehicle.

In the third scenario 606, the broadcast identifier information of thereceived data packet may include an individual identifier thatidentifies a single intended receiver for the data packet. In thisscenario 606, the individual identifier of the data packet is comparedto a locally stored individual identifier of the recipient receiver thatmay be uniquely associated with the receiver. If the individualidentifiers match, then the data packet is determined to be directed tothe recipient receiver and vehicle. If the individual identifiers do notmatch, then the data packet is determined to not be directed at therecipient receiver and vehicle.

FIG. 7 is a flowchart of a process 700 for enabling communicationbetween a receiver receiving a datagram broadcast via a satellite radionetwork and a remote location such as a service center in accordancewith an embodiment of the present invention. In process 700, messages toa user may be transmitted via datagrams received by the satellite radionetwork receiver (e.g., receiver 330). In operation 702, a user mayissue a command to the receiver via a user interface (e.g., via userinterface 334) to review messages sent to the user via the satelliteradio network. Upon issuance of the command, information relating to themessage(s) may be obtained from the receiver and presented to the uservia the user interface (see operations 704, 706, 708). Process 700 mayalso include operations for decrypting the message is it is determinedto be encrypted (see operations 704, 706). If there are a plurality ofmessages, a listing of the messages may be presented to the user.

The user may then select for review one of the messages from the listingof messages in operation 710 and the selected message may then bepresented either visually or audibly to the user (see operation 712). Ifthe selected message indicates that the user needs to contact a remotelocation such as, for example, a service center, the user may then issuea command to contact (via a cellular communication) the remote locationvia the user interface (see operation 714). Upon issuing of thiscommand, the receiver may then retrieve a telephone number associatedwith the remote location that was stored with or as part of the messagein the local memory of the receiver and then initiate a cellularcommunication link with the remote located using the retrieved telephonenumber and a cellular communication transmitter/receiver coupled to thereceiver (e.g., cellular communication component 430) (see operations716, 718). The process set forth in FIG. 7 may be utilized to permitchanging of a group identifier of a receiver via cellular wirelesscommunication link. In such an embodiment, after the remote location hasbeen contacted, the remote location could issue a group identifierchange command via the cellular wireless communication link in a mannersimilar to that previously set forth.

In an embodiment of the present invention, the satellite radio networkmay comprise a satellite digital audio radio service (SDARS) networksuch as that provided by XM Satellite Radio (formerly American MobileRadio) and Sirius Satellite Radio (formerly CD Radio). These satelliteradio networks function in a spectrum in the S band allocated by the FCCfor digital satellite radio transmissions. Another satellite digitalaudio radio service provided by WorldSpace provided satellite radiobroadcasts in other regions of the world such as Asia and Africa. Anexemplary embodiment of a satellite digital audio radio service networkis set forth in U.S. Pat. No. 6,510,317 to Marko et al. entitled,“Satellite Digital Audio Radio Service Tuner Architecture for Receptionof Satellite and Terrestrial Signals.” In particular, an exemplarysatellite radio network may include a plurality of geostationarysatellites which transmit line-of-sight signals to satellite radioreceivers. The satellites may provide for interleaving and spatialdiversity however, the signals from the two satellites could be delayedto provide time diversity. The satellite radio network may also includea plurality of terrestrial repeaters (including non-line of sightrepeaters) may also be which receive and retransmit the satellitesignals to the satellite radio receivers in order to facilitate reliablereception in geographic areas where line of sight reception from thesatellites is obscured by tall buildings, hills, tunnels and otherobstructions. The satellite receivers may be located in automobiles,handheld units, and/or stationary units.

A Global Positioning System (GPS) comprises a number of satellitesorbiting the Earth that make it possible for user with GPS receivers topinpoint their geographic location. In general, the satellites may bespaced apart so that from any point on Earth, four satellites will beabove the horizon. Each satellite contains a computer, an atomic clock,and a radio. With an understanding of its own orbit and the clock, thesatellite continually broadcasts its changing position and time. (Once aday, each satellite checks its own sense of time and position with aground station and makes any minor correction.) The GPS receiverincludes a computer that “triangulates” its own position by gettingbearings from three of the four satellites. The result is provided inthe form of a geographic position in longitude and latitude. A GPSreceiver may also be equipped with a display screen that shows a map sothat the receiver's position can be shown on the map. In addition, if afourth satellite may be received, the receiver/computer may be able tocalculate the altitude of the receiver.

In the present description, the various sub-components of each of thecomponents may also be considered components of the system. For example,particular software modules executed on any component of the system mayalso be considered components of the system. Components of embodimentsof the present invention may be implemented on computers having acentral processing unit such as a microprocessor, and a number of otherunits interconnected via a bus. Such computers may also include RandomAccess Memory (RAM), Read Only Memory (ROM), an I/O adapter forconnecting peripheral devices such as, for example, disk storage unitsand printers to the bus, a user interface adapter for connecting varioususer interface devices such as, for example, a keyboard, a mouse, aspeaker, a microphone, and/or other user interface devices such as atouch screen or a digital camera to the bus, a communication adapter forconnecting the workstation to a communication network (e.g., a dataprocessing network) and a display adapter for connecting the bus to adisplay device. The workstation may utilize an operating system such as,for example, a Microsoft Windows Operating System (OS), a Macintosh OS,a Linux OS and/or a UNIX OS. Those skilled in the art will appreciatethat the present invention may also be implemented on platforms andoperating systems other than those mentioned. Embodiments of the presentinvention may also be implemented using computer program languages suchas, for example, ActiveX , Java, C, and the C++ language and utilizeobject oriented programming methodology.

Transmission Control Protocol/Internet Protocol (TCP/IP) is a basiccommunication language or protocol of the Internet. It can also be usedas a communications protocol in the private networks called intranet andin extranet. TCP/IP is a two-layering program. The higher layer,Transmission Control Protocol (TCP), manages the assembling of a messageor file into smaller packet that are transmitted over the Internet andreceived by a TCP layer that reassembles the packets into the originalmessage. The lower layer, Internet Protocol (IP), handles the addresspart of each packet so that it gets to the right destination. Eachgateway computer on the network checks this address to see where toforward the message. Even though some packets from the same message arerouted differently than others, they'll be reassembled at thedestination.

TCP/IP uses a client/server model of communication in which a computeruser (a client) requests and is provided a service (such as sending aWeb page) by another computer (a server) in the network. TCP/IPcommunication is primarily point-to-point, meaning each communication isfrom one point (or host computer) in the network to another point orhost computer. TCP/IP and the higher-level applications that use it arecollectively said to be “stateless” because each client request isconsidered a new request unrelated to any previous one (unlike ordinaryphone conversations that require a dedicated connection for the callduration). Being stateless frees network paths so that everyone can usethem continuously. (Note that the TCP layer itself is not stateless asfar as any one message is concerned. Its connection remains in placeuntil all packets in a message have been received.).

Protocols related to TCP/IP include the User Datagram Protocol (UDP),which is used instead of TCP for special purposes. Other protocols areused by network host computers for exchanging router information. Theseinclude the Internet Control Message Protocol (ICMP), the InteriorGateway Protocol (IGP), the Exterior Gateway Protocol (EGP), and theBorder Gateway Protocol (BGP).

Internetwork Packet Exchange (IPX)is a networking protocol from Novellthat interconnects networks that use Novell's NetWare clients andservers. IPX is a datagram or packet protocol. IPX works at the networklayer of communication protocols and is connectionless (that is, itdoesn't require that a connection be maintained during an exchange ofpackets as, for example, a regular voice phone call does).

Packet acknowledgment is managed by another Novell protocol, theSequenced Packet Exchange (SPX). Other related Novell NetWare protocolsare: the Routing Information Protocol (RIP), the Service AdvertisingProtocol (SAP), and the NetWare Link Services Protocol (NLSP).

A virtual private network (VPN) is a private data network that makes useof the public telecommunication infrastructure, maintaining privacythrough the use of a tunneling protocol and security procedures. Avirtual private network can be contrasted with a system of owned orleased lines that can only be used by one company. The idea of the VPNis to give the company the same capabilities at much lower cost by usingthe shared public infrastructure rather than a private one. Phonecompanies have provided secure shared resources for voice messages. Avirtual private network makes it possible to have the same securesharing of public resources for data.

Using a virtual private network involves encryption data before sendingit through the public network and decrypting it at the receiving end. Anadditional level of security involves encrypting not only the data butalso the originating and receiving network addresses. Microsoft, 3Com,and several other companies have developed the Point-to-Point TunnelingProtocol (PPP) and Microsoft has extended Windows NT to support it. VPNsoftware is typically installed as part of a company's firewall server.

Wireless refers to a communications, monitoring, or control system inwhich electromagnetic radiation spectrum or acoustic waves carry asignal through atmospheric space rather than along a wire. In mostwireless systems, radio frequency (RF) or infrared transmission (IR)waves are used. Some monitoring devices, such as intrusion alarms,employ acoustic waves at frequencies above the range of human hearing.Common examples of wireless equipment in use today include the GlobalPositioning System, cellular telephone phones and pagers, cordlesscomputer accessories (for example, the cordless mouse),home-entertainment-system control boxes, remote garage-door openers,two-way radios, and baby monitors. An increasing number of companies andorganizations are using wireless LAN. Wireless transceivers areavailable for connection to portable and notebook computers, allowingInternet access in selected cities without the need to locate atelephone jack. Eventually, it will be possible to link any computer tothe Internet via satellite, no matter where in the world the computermight be located.

Bluetooth is a computing and telecommunications industry specificationthat describes how mobile phones, computers, and personal digitalassistants (PDA's) can easily interconnect with each other and with homeand business phones and computers using a short-range wirelessconnection. Each device is equipped with a microchip transceiver thattransmits and receives in a previously unused frequency band of 2.45 GHzthat is available globally (with some variation of bandwidth indifferent countries). In addition to data, up to three voice channelsare available. Each device has a unique 48-bit address from the IEEE 802standard. Connections can be point-to-point or multipoint. The maximumrange is 10 meters. Data can be presently be exchanged at a rate of 1megabit per second (up to 2 Mbps in the second generation of thetechnology). A frequency hop scheme allows devices to communicate evenin areas with a great deal of electromagnetic interference. Built-inencryption and verification is provided.

Encryption is the conversion of data into a form, called a ciphertext,that cannot be easily understood by unauthorized people. Decryption isthe process of converting encrypted data back into its original form, soit can be understood.

Rivest-Shamir-Adleman (RSA) is an Internet encryption and authenticationsystem that uses an algorithm developed in 1977 by Ron Rivest, AdiShamir, and Leonard Adleman. The RSA algorithm is a commonly usedencryption and authentication algorithm and is included as part of theWeb browser from Netscape and Microsoft. It's also part of Lotus Notes,Intuit's Quicken, and many other products. The encryption system isowned by RSA Security.

The RSA algorithm involves multiplying two large prime numbers (a primenumber is a number divisible only by that number and 1) and throughadditional operations deriving a set of two numbers that constitutes thepublic key and another set that is the private key. Once the keys havebeen developed, the original prime numbers are no longer important andcan be discarded. Both the public and the private keys are needed forencryption/decryption but only the owner of a private key ever needs toknow it. Using the RSA system, the private key never needs to be sentacross the Internet.

The private key may be used to decrypt text that has been encrypted withthe public key. For example, to send a message to a recipient, a senderfirst obtains the recipient's public key (but not the recipient'sprivate key) from a central administrator and encrypt the message usingthe recipient's public key. When the recipient receives the encryptedmessage from the sender, the recipient may then decrypt the encryptedmessage with the recipient's private key. In addition to encryptingmessages (which ensures privacy), senders may also authenticatethemselves to recipients (so that the recipient can verify the identityof the sender) by using the sender's own private key to encrypt adigital certificate. When the recipient receives the digitalcertificate, the recipient can use the sender's public key to decryptit.

The Secure Sockets Layer (SSL) is a commonly-used protocol for managingthe security of a message transmission on the Internet. SSL has recentlybeen succeeded by Transport Layer Security (TLS), which is based on

SSL. SSL uses a program layer located between the Internet's HypertextTransfer Protocol (HTTP) and Transport Control Protocol (TCP) layers.SSL uses the public-and-private key encryption system from RSA, whichalso includes the use of a digital certificate. A SSL protocol isdescribed in the SSL Protocol Version 3.0 by the Transport LayerSecurity Working Group, Nov. 18, 1996 for providing communicationsprivacy over the Internet and allowing client/server applications tocommunicate in a way that is designed to prevent eavesdropping,tampering, or message forgery, the disclosure of which is incorporatedherein by reference in its entirety.

Transport Layer Security (TLS) is a protocol that ensures privacybetween communicating applications and their users on the Internet. Whena server and client communicate, TLS ensures that no third party mayeavesdrop or tamper with any message. TLS is a successor to the SecureSockets Layer (SSL). TLS is composed of two layers: the TLS RecordProtocol and the TLS Handshake Protocol. The TLS Record Protocolprovides connection security with some encryption method such as theData Encryption Standard (DES). The TLS Record Protocol can also be usedwithout encryption. The TLS Handshake Protocol allows the server andclient to authenticate each other and to negotiate an encryptionalgorithm and cryptographic keys before data is exchanged. The TLSprotocol is based on Netscape's SSL 3.0 protocol; however, TLS and SSLare not interoperable. The TLS protocol does contain a mechanism thatallows TLS implementation to back down to SSL 3.0. A TLS protocol isdescribed in the document entitled, “The TLS Protocol, Version 1” by theNetwork Working Group of the Internet Society, 1999, the disclosure ofwhich is incorporated herein by reference in its entirety. This documentspecifies Version 1.0 of the Transport Layer Security (TLS) protocol.The TLS protocol provides communications privacy over the Internet. Theprotocol allows client/server applications to communicate in a way thatis designed to prevent eavesdropping, tampering, or message forgery.

Wireless Transport Layer Security (WTLS) is the security level forWireless Application Protocol (WAP) applications. Based on TransportLayer Security (TLS) v1.0 (a security layer used in the Internet,equivalent to Secure Socket Layer 3.1), WTLS was developed to addressthe problematic issues surrounding mobile network devices—such aslimited processing power and memory capacity, and low bandwidth—and toprovide adequate authentication, data integrity, and privacy protectionmechanisms.

The Wired Equivalent Privacy (WEP) algorithm, is part of the 802.11standard. The 802.11 standard describes the communication that occurs inwireless local area networks (LANs). The Wired Equivalent Privacy (WEP)algorithm is used to protect wireless communication from eavesdropping.A secondary function of WEP is to prevent unauthorized access to awireless network; this function is not an explicit goal in the 802.11standard, but it is frequently considered to be a feature of WEP. WEPrelies on a secret key that is shared between a mobile station (e.g. alaptop with a wireless Ethernet card) and an access point (i.e. a basestation). The secret key is used to encrypt packets before they aretransmitted, and an integrity check is used to ensure that packets arenot modified in transit. The standard does not discuss how the sharedkey is established. In practice, most installations use a single keythat is shared between all mobile stations and access points.

Based on the foregoing specification, the invention may be implementedusing computer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting program, having computer-readable code means, may beembodied or provided within one or more computer-readable media, therebymaking a computer program product, i.e., an article of manufacture,according to the invention. The computer readable media may be, forinstance, a fixed (hard) drive, diskette, optical disk, magnetic tape,semiconductor memory such as read-only memory (ROM), etc., or anytransmitting/receiving medium such as the Internet or othercommunication network or link. The article of manufacture containing thecomputer code may be made and/or used by executing the code directlyfrom one medium, by copying the code from one medium to another medium,or by transmitting the code over a network.

One skilled in the art of computer science will easily be able tocombine the software created as described with appropriate generalpurpose or special purpose computer hardware to create a computer systemor computer sub-system embodying the method of the invention.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

1. A method for receiving data from a satellite radio network,comprising: a) receiving at a first receiver a packet of data comprisinga header portion and a body portion broadcast via a satellite radionetwork, wherein the header portion of the packet of data includesbroadcast identifier information that is associated with a selected setof receivers configured to receive the broadcast that are intendedrecipients of the packet of data; b) determining if the first receiveris a member of the selected set of receivers configured to receive thebroadcast that are intended recipients of the packet of data using thebroadcast identifier information; and c) processing the packet of dataif the first receiver is determined to be a member of the selected setof receivers configured to receive the broadcast that are intendedrecipients of the packet of data.
 2. The method of claim 1, wherein thefirst receiver is located in a vehicle.
 3. The method of claim 1,wherein the broadcast identifier information included in the headerportion of the packet of data is compared with locally stored identifierinformation associated with the first receiver to determine if the firstreceiver is a member of the selected set of receivers configured toreceive the broadcast that are intended recipients of the packet ofdata.
 4. The method of claim 3, wherein a user of the first receiverdefines at least a portion of the locally stored identifier informationthat is compared with the broadcast identifier information.
 5. Themethod of claim 1, wherein the broadcast identifier information includesinformation identifying a geographic area to which the packet of data isdirected, and wherein the broadcast identifier information is comparedwith information about a geographic location of the first receiver todetermine whether the first receiver is in the geographic area to whichthe packet of data is directed.
 6. The method of claim 1, wherein thepacket of data includes an instruction to modify at least a portion oflocally stored identifier information of the first receiver, and whereinthe processing of the packet of data includes modifying the locallystored identifier information according to the instruction.
 7. Themethod of claim 1, wherein the packet of data includes one or more ofaudio and video information, and wherein processing of the packet ofdata includes presenting the one or more of audio and visual informationincluded in the packet of data using a user interface coupled to thefirst receiver.
 8. A system for receiving data from a satellite radionetwork, comprising: a first receiver for receiving a packet of datacomprising a header portion and a body portion broadcast via a satelliteradio network, wherein the header portion of the packet of data includesbroadcast identifier information that is associated with a selected setof receivers configured to receive the broadcast that are intendedrecipients of the packet of data; a processor for determining if thefirst receiver is a member of the selected set of receivers configuredto receive the broadcast that are intended recipients of the packet ofdata using the broadcast identifier information; and wherein theprocessor processes the packet of data if the first receiver isdetermined to be a member of the selected set of receivers configured toreceive the broadcast that are intended recipients of the packet ofdata.
 9. The system of claim 8, wherein the first receiver is located ina vehicle.
 10. The system of claim 8, further comprising locally storedidentifier information stored in memory coupled to the first receiver;and wherein the broadcast identifier information included in the headerportion of the packet of data is compared with the locally storedidentifier information to determine if the first receiver is a member ofthe selected set of receivers configured to receive the broadcast thatare intended recipients of the packet of data.
 11. The system of claim10, wherein the packet of data includes an instruction to modify atleast a portion of locally stored identifier information of the firstreceiver, and wherein the processing of the packet of data includesmodifying the locally stored identifier information according to theinstruction.
 12. The system of claim 8, wherein the broadcast identifierinformation includes information identifying a geographic area to whichthe packet of data is directed, and wherein the broadcast identifierinformation is compared with information about a geographic location ofthe first receiver to determine whether the first receiver is in thegeographic area to which the packet of data is directed.
 13. The systemof claim 8, further comprising a user interface coupled to the firstreceiver; wherein the packet of data includes one or more of audio andvideo information; and wherein the processor presents the one or more ofaudio and visual information included in the packet of data via the userinterface.
 14. A system for broadcasting data for transmission via asatellite radio network, comprising: logic for preparing a packet ofdata for broadcast, wherein the packet of data comprises a headerportion and a body portion, and wherein the header portion of the packetof data further comprises broadcast identifier information associatedwith a selected set of receivers configured to receive the broadcastthat are intended recipients of the packet of data; a transmitter forbroadcasting the packet of data including the header portion with thebroadcast identifier information; and a receiver for receiving anotification confirming that at least one intended recipient in theselected set of receivers has received the packet of data.
 15. Thesystem of claim 14, wherein at least one of the receivers in theselected set of receivers is located in a vehicle.
 16. The system ofclaim 14, wherein the broadcast identifier information includesinformation identifying a geographic area to which the packet of data isdirected, and wherein the broadcast identifier information is comparedwith information about a geographic location of the at least oneintended recipient receiver to determine whether the at least oneintended recipient receiver is in the geographic area to which thepacket of data is directed.
 17. The system of claim 14, wherein thepacket of data includes an instruction to modify at least a portion oflocally stored identifier information of each of the receivers in theselected set of receivers that are intended recipients of the packet ofdata.
 18. The system of claim 17, wherein the notification is receivedupon modification of the locally stored identifier information in the atleast one intended recipient in the selected set of receivers.
 19. Thesystem of claim 14, wherein the notification is received via a cellularwireless communication link.
 20. The system of claim 14, wherein adatabase of information relating to the selected set of receiversconfigured to receive the broadcast that are intended recipients of thepacket of data is updated upon receipt of the notification.